Is it possible to export a specific view of a DOORS module to a dma file? Or do I need to create another module with that view and export the new module to a dma? Thank you! Ying yhisella - Thu Mar 19 16:45:26 EDT 2015 |
Re: Export a specific view of a module to dma Try making all Views private except the one you want to export. Export your dma, then change the Views back to their previous permissions. The person that restores the Module will only see the View that you didn't make private. |
Re: Export a specific view of a module to dma If you are asking to restrict the information inside the module archive (dma) to the contents of a view, then NO. A DOORS module archive is what it says, an archive of a complete module including history, all attributes, values, views, links, etc. (Yes the links are contained in a module archived, they just won't be restored). If you want to protect certain sensitive information, you would indeed create a new module (but be careful that the absolute numbers might change, if you do not take special care about this). Note that you can filter the object hierarchy to not show parent objects of some objects, so you cannot safely assume that you can convert the objects inside a view to a consistent object hierarchy. Regards, Mathias |
Re: Export a specific view of a module to dma woodpryan - Thu Mar 19 17:48:52 EDT 2015 Try making all Views private except the one you want to export. Export your dma, then change the Views back to their previous permissions. The person that restores the Module will only see the View that you didn't make private. This worked out perfectly. Thanks for the great idea. |
Re: Export a specific view of a module to dma Mathias Mamsch - Fri Mar 20 11:03:43 EDT 2015 If you are asking to restrict the information inside the module archive (dma) to the contents of a view, then NO. A DOORS module archive is what it says, an archive of a complete module including history, all attributes, values, views, links, etc. (Yes the links are contained in a module archived, they just won't be restored). If you want to protect certain sensitive information, you would indeed create a new module (but be careful that the absolute numbers might change, if you do not take special care about this). Note that you can filter the object hierarchy to not show parent objects of some objects, so you cannot safely assume that you can convert the objects inside a view to a consistent object hierarchy. Regards, Mathias Thanks for your insightful comments Mathias. The information we are trying to exclude from the archive are a subset of attributes for internal use only. Based on your inputs, we changed the access for these attributes so that it would not be viewable by external users. Pending confirmation, we think this will work well. By the way, you are right about the absolute numbers of a new module. Can you please share what special care needs be taken to ensure the absolute numbers are the same as the copied module? Ying |
Re: Export a specific view of a module to dma Why not still use the archive? Then restore the module and run a script to delete all unwanted attributes and views. IDs stay intact. We use a Delivery Control module that lists modules, attributes and views to be included in the delivery. The script reads the module, archives and restores to the Delivery Project area. Then it opens each restored module and deletes all custom views/attributes not listed in the control module. If delivery needs change, the control module gets updated, no script change needed. The added benefit is for each delivery you have an easy way of identifying what was sent to the customer for each delivery (five years later sometimes this is hard to find). The script needs to be run from the Administrator account to be able to delete private views. |
Re: Export a specific view of a module to dma smarti.sj - Tue Mar 24 08:32:02 EDT 2015 Why not still use the archive? Then restore the module and run a script to delete all unwanted attributes and views. IDs stay intact. We use a Delivery Control module that lists modules, attributes and views to be included in the delivery. The script reads the module, archives and restores to the Delivery Project area. Then it opens each restored module and deletes all custom views/attributes not listed in the control module. If delivery needs change, the control module gets updated, no script change needed. The added benefit is for each delivery you have an easy way of identifying what was sent to the customer for each delivery (five years later sometimes this is hard to find). The script needs to be run from the Administrator account to be able to delete private views. careful! It might happen that the "Administrator" of the receiving database can see the history of the objects, where the internal attributes have been changed. You might want to do a baseline in your delivery project area after you deleted the internal attributes and ensure that baselines are not included in the archive. |
Re: Export a specific view of a module to dma Mike.Scharnow - Tue Mar 24 09:06:49 EDT 2015 careful! It might happen that the "Administrator" of the receiving database can see the history of the objects, where the internal attributes have been changed. You might want to do a baseline in your delivery project area after you deleted the internal attributes and ensure that baselines are not included in the archive. yes Mike! thanks! I forgot that part - script baselines all the restored modules as well after the deletes are complete. Then finally the script archives the delivery project without baselines eliminating all the nasty history of the illicit deletes : ) |
Re: Export a specific view of a module to dma smarti.sj - Tue Mar 24 09:20:04 EDT 2015 yes Mike! thanks! I forgot that part - script baselines all the restored modules as well after the deletes are complete. Then finally the script archives the delivery project without baselines eliminating all the nasty history of the illicit deletes : ) Excellent idea! We will try this next time. Thank you both! |